E-ink touchscreen visualizer for home AV system

ABSTRACT

An interface apparatus includes a main unit, an array of interface modules, driver circuitry, and a remote unit. The main unit outputs files to an output unit, is detachably couplable to interface modules and assigns content identifiers to interface modules. The array presents an image to the user and each interface module can be engaged by a user. The driver circuitry is adapted to drive the array to present an image to the user based upon the user&#39;s engagement with an interface module. The remote unit is coupled to the output unit and can be detachably coupled to the interface module. When coupled to the interface module, the remote unit can access the assigned identifier and transmit a request signal to the main unit based on the identifier. The request signal is adapted to cause the main unit to output a file identified by the identifier to the output unit.

BACKGROUND

1. Field of Invention

Embodiments described herein of the present invention relates generallyto interfaces for home audio/video (AV) systems, and more specificallyto an interface apparatus that facilitates a user's interaction with ahome AV system and a method of using the same.

2. Discussion of the Related Art

Conventional home audio/video (AV) systems output media files (e.g.,songs) to output units that include speakers. Typically, these home AVsystems display the title of media files when they are output to theoutput units. Often, the title is displayed in a textual or thumbnailformat that is either not aesthetically pleasing or is difficult to viewunless the user is close to the main unit of the home AV system.Moreover, existing home AV systems do not allow users to select theirfavorite media files in an easy one-step action.

SUMMARY

Several embodiments of the invention advantageously address the needsabove as well as other needs by providing an e-ink touchscreenvisualizer for a home AV system.

One embodiment exemplarily disclosed herein relates to an interfaceapparatus that includes a main unit, an array of interface modulescoupled to the main unit, and driver circuitry. The main unit is adaptedto cause media files to be output to an output unit. The array ofinterface modules is adapted to present an image to the user. Moreover,each interface module in the array of interface modules is adapted to beengaged by a user and generate a signal when engaged by the user. Thedriver circuitry is adapted to drive the array of interface modules topresent an image to the user based at least in part upon a signalgenerated by a user's engagement with an interface module.

Another embodiment exemplarily disclosed herein relates to an interfaceapparatus that includes an interface module, a main unit, drivercircuitry, and a remote unit coupled to the output unit. The interfacemodule is adapted to be driven to present an image to a user. The mainunit is adapted to cause media files to be output to an output unit.Further, the main unit is adapted to be detachably coupled to theinterface module and, when coupled to the interface module, to assign acontent identifier to the interface module that identifies a media file.The driver circuitry is adapted to drive the interface module to presentan image corresponding to the assigned content identifier. The remoteunit is adapted to be detachably coupled to the interface module. Whencoupled to the interface module, the remote unit is adapted to accessthe content identifier assigned to the interface module coupled theretoand transmit a media file request signal to the main unit based on thecontent identifier. The media file request signal is adapted to causethe main unit to output a media file identified by the contentidentifier to the output unit.

Yet another embodiment exemplarily disclosed herein relates to aninterface method that includes driving an array of interface modulescoupled to a main unit to present an image across the array of interfacemodules based upon output characteristics of media files adapted to becaused to be output to an output unit via the main unit, generating asignal upon a user's engagement with an interface module, and updatingthe image presented across the array of interface modules based at leastin part upon the signal generated upon the user's engagement with theinterface module.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects and features of several embodimentsdescribed herein will be more apparent from the following moreparticular description thereof, presented in conjunction with thefollowing drawings.

FIG. 1 illustrates one embodiment of an interface apparatus in which anexemplary home AV system incorporates a main unit;

FIG. 2 illustrates one embodiment of interface module incorporatedwithin the interface apparatus shown in FIG. 1;

FIG. 3 illustrates an exemplary functional block diagram of componentswithin the interface apparatus shown in FIG. 1;

FIG. 4 illustrates a flow chart describing one embodiment of a methodfor driving the array of interface modules shown in FIG. 1 to presentimages across the array of interface modules;

FIG. 5 illustrates an array of interface modules driven to present anexemplary composite image comprising a plurality of constituent images;

FIG. 6 illustrates an array of interface modules driven to present anexemplary scaled image associated with a constituent image shown in FIG.5;

FIG. 7 illustrates an array of interface modules driven to present anexemplary content-information image associated with the scaled imageshown in FIG. 6;

FIG. 8 illustrates another embodiment of an interface apparatus in whichan exemplary output unit of a home AV system incorporates a remote unit;

FIG. 9 illustrates an exemplary functional block diagram of componentswithin the interface apparatus shown in FIG. 8; and

FIG. 10 illustrates a flow chart describing one embodiment of a methodin which media files can be output to the output unit shown in FIG. 8.

Corresponding reference characters indicate corresponding componentsthroughout the several views of the drawings. Skilled artisans willappreciate that elements in the figures are illustrated for simplicityand clarity and have not necessarily been drawn to scale. For example,the dimensions of some of the elements in the figures may be exaggeratedrelative to other elements to help to improve understanding of variousembodiments exemplarily described herein. Also, common butwell-understood elements that are useful or necessary in a commerciallyfeasible embodiment are often not depicted in order to facilitate a lessobstructed view of these various embodiments.

DETAILED DESCRIPTION

The following description is not to be taken in a limiting sense, but ismade merely for the purpose of describing the general principles ofexemplary embodiments. The scope of the invention should be determinedwith reference to the claims.

As used herein, the term “component” is intended to refer to acomputer-related entity, either hardware, a combination of hardware andsoftware, software, or software in execution. For example, a componentcan be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. One or more components can reside within a processand/or thread of execution, and a component can be localized on onecomputer and/or distributed between two or more computers. As usedherein, the term “memory” is intended to refer to a computer-readablestorage medium and/or device such as read access memory (RAM), read onlymemory (ROM), a hard disk drive, optical disk/optical disk drive,magnetic disk/magnetic disk drive, and the like, and combinationsthereof.

According to numerous embodiments disclosed herein, an interfaceapparatus of a home AV system visually presents information associatedwith media files to users in an aesthetically pleasing manner and allowsusers to select media files to play with ease. FIG. 1 illustrates oneembodiment of such an interface apparatus of an exemplary home AV system100.

As shown in FIG. 1, the interface apparatus includes a main unit 102 andan array of interface modules 104. As shown in FIG. 1, the exemplaryhome AV system 100 may include an output unit 106, a plurality ofspeakers 108, and a communication link 110.

Generally, the main unit 102 can be provided as any device suitable foroutputting (or causing to be output) media files (e.g., music, pictures,movies, electronic documents, or any other audio and/or video data) toone or more output units such as output unit 106. According to numerousembodiments disclosed herein, the main unit 102 is further adapted todrive the array of interface modules 104 in a manner that causes animage (e.g., a composite image, a scaled image, a content-informationimage, as will be described in greater detail below with respect toFIGS. 4-7) to be presented by the array of interface modules 104.

In the illustrated embodiment, the array of interface modules 104 isessentially a square/rectangular array and can be attached to anddetached from (i.e., detachably coupled to) the main unit 102 via anysuitable means (e.g., magnetically or mechanically via atounge-in-groove arrangement between cooperative surfaces of the mainunit 102 and the interface modules 104, latch, clip, or the like, orcombinations thereof). It will be appreciated, however, that theplurality of interface modules 104 may be arranged in any desiredpattern. As illustrated, the array of interface modules is comprised ofnine individual interface modules 104. It will be appreciated however,that the array of interface modules may comprise more or less numbers ofindividual interface modules 104. Moreover, it will be appreciated thatthe interface apparatus may include more interface modules 104 than canbe coupled to the main unit 102 at one time.

FIG. 2 illustrates one embodiment of an interface module 104incorporated within the interface apparatus shown in FIG. 1. As shown inFIG. 2, each interface module 104 includes a module housing 202 and atouch-sensitive display 204 mounted to the module housing 202. Themodule housing 202 further contains other components described ingreater detail with respect to FIG. 3. The touch-sensitive display 204is adapted to present images in an electronically controllable manner.As will be described in greater detail below, the touch-sensitivedisplay 204 is also adapted to generate engagement signals upon beingengaged (e.g., touched) by the user (e.g., via the user's finger, via astylus held by the user, etc.). Suitable touch-sensitive displays thatmay be incorporated within the interface module 104 include, forexample, e-ink displays (also known as electronic paper, electronic ink,and e-paper) fitted with touch-screen elements (e.g., resistive,electromagnetic, etc.), all of which are well known in the art. It willalso be appreciated that, instead of an e-ink display, other types ofelectronically controllable displays (e.g., LCD, OLED, etc.) may also beused.

Referring back to FIG. 1, the output unit 106 includes the plurality ofspeakers 108 and is communicatively coupled to the main unit 102 via thecommunication link 110 (e.g., one or more wired or wirelesscommunication paths). While the embodiment illustrated in FIG. 1exemplarily depicts only one output unit 106 as a speaker unitcontaining the plurality of speakers 108 capable of presenting sound(e.g., as music, voice, etc.), it will be appreciated that the outputunit 106 can be provided as any type of device (e.g., computer, monitor,television, projector, personal digital assistant, cellular phone, etc.)capable of presenting any type of media file to a user and that anynumber of output units may be communicatively coupled to the main unit102 via one ore more communication links 110.

FIG. 3 illustrates an exemplary functional block diagram of componentswithin the interface apparatus shown in FIG. 1. Generally, FIG. 3illustrates functional components of the main unit 102 and an interfacemodule 104. As shown, the main unit 102 includes a main controllercomponent 302, a main memory 304, a main output component 306, anoptional main driver component 308, and a main communication component310. An exemplary interface module 104 is shown to include a modulecontroller component 312, an optional module driver component 314, thetouch-sensitive display 204, and a module communication component 316.

As illustrated, the main controller component 302 is connected to themain memory 304, the main output component 306, and the maincommunication component 310 while the module controller component 312 isconnected the module communication component 316 and the touch-sensitivedisplay 204. In one embodiment, the main unit 102 includes the maindriver component 308. In such an embodiment, the main driver component308 is connected between an output of the main controller component 302and an input of the main communication component 310 and the moduledriver component 314 is not included within the interface module 104. Inanother embodiment, the interface module 104 includes the module drivercomponent 314. In such an embodiment, the module driver component 314 isconnected between an output of the module controller component 312 andan input of the touch-sensitive display 204 and the main drivercomponent 308 is not included within the main unit 102.

The main memory 304 is adapted to store media files in a manner that isaccessible by the main controller component 302. Each media file storedwithin the main memory 304 is uniquely identified within the main memory304 by a content identifier. Generally, media files can be any digitalaudio or video files, in any format. Aside from the actual audio and/orvideo content to be presented via the output unit 106, media files alsoinclude descriptors of attributes associated with the audio/videocontent. For example, if a media file is an album comprising acollection of tracks, the attributes associated with the album caninclude album title, song titles, etc., and descriptors of theattributes include the actual title of the album, song, etc. In oneembodiment, each media file may further include interface-imageinformation describing how that media file is to be visually identifiedto the user via one or more interface modules 104 within the array ofinterface modules. For example, if a media file is an album comprising acollection of songs, the interface-image information can describe animage such as cover art associated with the album.

The main controller component 302 is adapted to access media filesstored within the main memory 304 and output the accessed media files tothe output unit 106 based upon information contained within selectionsignals transmitted by one or more interface modules 104 within thearray of interface modules. In one embodiment, the main controllercomponent 302 outputs media files to the output unit 106 by generating adata stream containing one or more output signals. In one embodiment, anoutput signal generated by the main controller component 302 may includean output unit address adapted to ensure that media files are outputonly to selected output units associated with the output unit addressincluded within the data stream.

The main controller component 302 is adapted to generate imageinformation based on information contained within selection signalstransmitted by interface modules 104 within the array of interfacemodules. As used herein, the term “image information” refers toinformation required by either the main or module driver components 308or 316, respectively, to drive each of the interface modules 104 withinthe array of interface modules to present the aforementioned composite,scaled, and content-information images. In one embodiment, the maincontroller component 302 is adapted to generate image information upondetermining which interface module 104 within the array of interfacemodules has been engaged (e.g., touched) by a user and/or upondetermining where a user has engaged (e.g., touched) an interface modulewithin the array of interface modules. Generally, the main controllercomponent 302 is adapted to make such determinations based oninformation contained within selection signals transmitted by engagedinterface modules 104.

In one embodiment, and as will be discussed in greater detail withrespect to FIGS. 4-7,the image information may also be generated basedon interface-image information associated with one or more media files.In a further embodiment, the image information may also be generatedbased on output characteristics of media files that the main unit 102can cause to be output at the output unit 106. An output characteristicof a media file that has been output by the main unit 102 may, forexample, include the time/date in which the media file was output to theoutput unit 106, the frequency with which the media file was output tothe output unit 106 (e.g., within a period of a week, month, year,etc.), or the like. The main output component 306 is adapted to processthe data stream (e.g., amplify output signals contained within the datastream, etc.) before media files are output to the output unit 106.

When the main driver component 308 is included within the main unit 102,the main controller component 302 outputs the image information to themain driver component 308 and the main driver component 308 converts theimage information into image data. The image data is then output by themain driver component 308 to the main communication component 310 whereit is transmitted to the interface modules 104 within the array ofinterface modules and ultimately used to drive each interface module 104in the array interface modules to present the aforementioned composite,scaled, and content-information images. When the main driver component308 is not included within the main unit 102, the main controllercomponent 302 outputs the image information to the main communicationcomponent 310.

The main and module communication components 310 and 316, respectively,are adapted to facilitate communication between the main unit 102 andthe interface module 104. Accordingly, the main communication component310 is adapted to transmit image information and/or image data to eachinterface module 104 within the array of interface modules and isfurther adapted to receive selection information from each interfacemodule 104 within the array of interface modules. Conversely, the modulecommunication component 316 of each interface module 104 within thearray of interface modules is adapted to transmit selection informationto the main unit 102 and is further adapted to receive image informationand/or image data from the main unit 102. In one embodiment, the mainand module communication components 310 and 316, respectively, areadapted to transmit/receive information/data wirelessly between the mainunit 102 and the associated interface module 104 within the array ofinterface modules and, therefore, may include any suitable type ofwireless receiver, transmitter, or transceiver. For example, the mainand module communication components 310 and 316, respectively, may eachinclude an antenna coupled to a radio frequency (RF) receiver,transmitter, or transceiver. In one embodiment, the main and modulecommunication components 310 and 316, respectively, may each becomprised within radio frequency identification (RFID) circuitryassociated with the main unit 102 and the interface module 104,respectively, such that electronics within the interface module 104(e.g., the module controller, driver, and communication components 312,314, and 316, respectively, and the touch-sensitive display 204) receivesufficient electrical power to function as described in the paragraphsbelow. Accordingly, and in one embodiment, each interface module 104 maynot include an internal power supply but, rather, operate based onelectricity generated by the interaction between the RFID circuitryassociated with the main unit 102 and the interface module 104. Inanother embodiment, the main and module communication components 310 and316, respectively, may be adapted to communicate with each other via anon-RFID means such as Bluetooth, Wi-Fi, etc. When, for example, eitherBluetooth, Wi-Fi, or the like, are used, each interface module 104includes an internal battery which can be charged while the interfacemodule 104 is coupled to the main unit 102. When the internal battery ischarged, the electronics within the interface module 104 receivesufficient electrical power to function as described in the paragraphsbelow.

The module controller component 312 is adapted to receive imageinformation/image data that has been transmitted to the modulecommunication component 316. When the module driver component 314 is notincluded within the interface module 104, the module controllercomponent 312 outputs image data directly to the touch-sensitive display204. However, when the module driver component 314 is included withinthe interface module 104, the module controller component 312 outputsimage information to the module driver component 314. The module drivercomponent 314 then converts the image information into image dataoutputs the image data to the touch-sensitive display 204.

When image data is output to the touch-sensitive display 204 of eachinterface module 104 in the array interface modules (either from themodule controller component 312 or the module driver component 314),each interface module 104 within the array of interface modules isdriven to present the aforementioned composite, scaled, andcontent-information images across the array of interface modules.Because the interface modules 104 within the array of interface modulescan be driven by various combinations of the main and module controllercomponents 302 and 312, respectively, and the main and module drivercomponents 308 and 314, respectively, these components can collectivelybe referred to as driver circuitry.

As mentioned above, the touch-sensitive display 204 is adapted togenerate engagement signals upon being engaged (e.g., touched) by theuser (e.g., via the user's finger or a stylus held by the user). In oneembodiment, the engagement signals contain engagement-locationinformation that represents a physical location where the user engagedthe touch-sensitive display 204. Accordingly, engagement signalsgenerated by the touch-sensitive display 204 represent a physicallocation of the user's engagement with the interface module 104. Thetouch-sensitive display 204 is further adapted to output the engagementsignals generated therein to the module controller component 312.

The module controller component 312 is further adapted receiveengagement signals output by the touch-sensitive display 204, generateone or more selection signals based on the received engagement signals,and output the selection signals to the module communication component316. In one embodiment, selection signals generated by the modulecontroller component 312 of an engaged interface module 104 containmodule identifier information that uniquely identifies the engagedinterface module 104 from other interface modules 104 within the arrayof interface modules. In another embodiment, selection signals generatedby the module controller component 312 of the engaged interface module104 contain module identifier information in addition to theaforementioned engagement-location information. The engagement-locationinformation included within the selection signals can be absolute (i.e.,identifying the physical location of the user's engagement with theengaged interface module 104 with respect to the engaged interfacemodule) or relative (i.e., identifying the physical location of theuser's engagement with the engaged interface module 104 with respect tothe array of interface modules). Having exemplarily described theinterface apparatus above, an exemplary method of driving the array ofinterface modules will now be described in greater detail below.

FIG. 4 illustrates a flow chart describing one embodiment of a methodfor driving the array of interface modules shown in FIG. 1 to presentimages across the array of interface modules.

At 402, the main controller component 302 generates image informationthat, when converted into image data, is adapted to drive each interfacemodule 104 within the array of interface modules to present a compositeimage across the array of interface modules. As used herein, a compositeimage is comprised of a plurality of constituent images and eachconstituent image visually identifies a media file stored within themain memory 304. As mentioned above, image information is generated at402 based upon interface-image information associated with one or moremedia files. Accordingly, each constituent image is presented within thearray of interface modules in accordance with interface-imageinformation associated with corresponding interface-image information.As also mentioned above, image information is generated at 402 basedupon output characteristics of one or more media files that the mainunit 102 can cause to be output at the output unit 106. Accordingly, thearray of interface modules can be driven to present a composite imagecomprised of a plurality of constituent images that visually identifyonly media files that have been recently output to the output unit 106,that have been frequently output to the output unit 106, etc.

FIG. 5 illustrates an exemplary composite image 502 comprised of aplurality of constituent images 504. As shown, each constituent image504 visually identifies a media file (e.g., a music album) via an image(e.g., cover art) presented in accordance with interface-imageinformation associated with that media file. Moreover, the compositeimage comprises only constituent images associated with media files thathave been recently output to the output unit 106, that have beenfrequently output to the output unit 106, or the like. In anotherembodiment, however, only one constituent image (e.g., the centerconstituent image) within the composite image is associated with a mediafile that has been recently output to the output unit 106, that has beenfrequently output to the output unit 106, or the like. In this case,constituent images surrounding the center constituent image areassociated with related media files (i.e., media files related to themedia file that has been recently output (or frequently output, etc.) tothe output unit 106 by artist, song, genre, etc.). Accordingly, aplurality of interface modules 104 may be driven to present thesurrounding constituent images based on meta data associated with themedia file visually identified by the center interface module 104, basedon recommendations provided by an internet service that pushes suchinformation to the main unit 102 over a network, etc.

In the embodiment illustrated in FIG. 5, each interface module 104 isdriven to present a single constituent image 504. In one embodiment,each interface module 104 may be driven to present a sequence ofconstituent images 504, wherein the constituent image presented by aninterface module 104 changes within a certain interval. As describedabove, the driver circuitry is adapted to drive each interface module104 within the array of interface modules to present a composite imageacross the array of interface modules, wherein the composite imagecomprises a plurality of the aforementioned constituent images.

Referring back to FIG. 4, at 404, an engagement signal is generated by atouch-sensitive display 204 of an interface module 104 that has beenengaged (e.g., touched) by a user. The engagement signal is then outputto the module controller component 312 incorporated within the engagedinterface module 104. The module controller component 312 subsequentlygenerates a selection signal that includes module identifier informationand/or engagement-location information. The selection signal is outputfrom the module controller component 312 to the module communicationcomponent 316, where it is subsequently transmitted to the maincontroller component 302 via the main communication component 310.

At 406, the main controller component 302 receives the selection signaltransmitted by the engaged interface module 104 at 404 and generatesimage information based on information contained within the receivedselection signal. The image information generated at 406, when convertedinto image data, is adapted to drive each interface module 104 withinthe array of interface modules to present scaled image associated with aconstituent image 504 presented by the engaged interface module 104across the array of interface modules.

FIG. 6 illustrates an array of interface modules driven to present anexemplary scaled image associated with a constituent image shown in FIG.5. As shown in FIG. 6, the scaled image 602 is an enlarged version ofthe constituent image 504 presented by the lower-right interface module104 in FIG. 5. Thus, FIG. 6 illustrates the result of a process whereinthe interface module 104 presenting the lower-right constituent image504 (shown in FIG. 5) has been engaged (e.g., touched) by a user, thetouch-sensitive display 204 of the engaged interface module 104 hasgenerated an engagement signal, the module controller component 312 ofthe engaged interface module 104 has generated a selection signalcontaining module identifier information and/or engagement-locationinformation, the selection signal has been transmitted to the maincontroller component 302 via the module and main communicationcomponents 316 and 310, respectively, and the main controller component302 has generated image information at 406 based upon the receivedselection signal. As described above, the driver circuitry is thereforeadapted to drive each interface module 104 within the array of interfacemodules to present a scaled image of the constituent image, presented byan engaged interface module 104, across the array of interface modulesbased upon an engagement signal generated by the engaged interfacemodule 104 (i.e., the interface module driven to present the constituentimage). That is, the driver circuitry is adapted to update the imagepresented across the array of interface modules based at least in partupon an engagement signal generated upon the user's engagement with aninterface module 104.

In one embodiment, and with reference to FIG. 6, the image informationgenerated at 406 includes icon-location information which, whenconverted into image data, is adapted to drive an interface module 104(e.g., the top-right interface module 104 within the array of interfacemodules) to present a revert-to-composite icon 604 at a predeterminedlocation on one or more interface modules 104 within the array ofinterface modules. While FIG. 6 illustrates only one icon presented byonly the top-right interface module 104, it will be appreciated that oneor more interface modules 104 within the array of interface modules maybe driven to present one or more icons simultaneous with thepresentation of the scaled image 602, as necessitated by thefunctionality provided by the interface apparatus. In one embodiment,the revert-to-composite icon 604 provides a visual indication of alocation where a user can engage an interface module 104 to cause thecomposite image 502, previously presented at 402, to be presented acrossthe array of interface modules, instead of the scaled image 602.

Referring back to FIG. 4, at 408, an engagement signal is generated by atouch-sensitive display 204 of an interface module 104 driven to presentthe revert-to-composite icon 604 upon being engaged (e.g., touched) by auser at a location corresponding to where the revert-to-composite icon604 is presented. When engagement-location information transmitted bythe engaged interface module 104 matches the icon-location informationgenerated at 406, the main controller component 302 generates imageinformation as described above at 402 which, when converted to imagedata, is adapted to drive each interface module 104 within the array ofinterface modules to present a composite image across the array ofinterface modules. Accordingly, the driver circuitry is adapted toupdate the image presented across the array of interface modules basedat least in part upon an engagement signal generated upon the user'sengagement with an interface module 104.

At 410, an engagement signal is generated by a touch-sensitive display204 of an interface module 104 that has been engaged (e.g., touched) bya user at a location corresponding to where the revert-to-composite icon604 is not presented and selection signal is generated by the modulecontroller component 312 associated with the engaged interface module104. The selection signal is then transmitted by the engaged interfacemodule 104 to the main controller component 302 via the module and maincommunication components 316 and 310, respectively. In one embodiment,the selection signal generated at 410 includes the module-identifierinformation. In another embodiment, the selection signal generated at410 includes engagement-location information. In another embodiment, theselection signal generated at 410 includes module-identifier informationand engagement-location information.

At 412, the main controller component 302 receives the selection signaltransmitted by the engaged interface module 104 and generates imageinformation based on the received selection signal. The imageinformation generated at 412, when converted into image data, is adaptedto drive each interface module 104 within the array of interface modulesto present a content-information image across the array of interfacemodules. In one embodiment, the content-information image visuallyidentifies one or more of the aforementioned descriptors of attributesassociated with the scaled image presented by the array of interfacemodules at 406.

FIG. 7 illustrates an exemplary content-information image 702. As shownin FIG. 7, the content-information image 702 visually identifies adescriptor of an album title attribute at 704 (e.g., “Hard Groove”) anddescriptors of song title attributes at 706 (e.g., “Hardgroove”, “CommonFree Style”, “I'll Stay”, “Mystic Bounce”, “Poster ‘T’”, “Poetry”,etc.). As also shown, the content-information image also visuallyidentifies a now-playing-indicator 708 identifying particular a trackthat is currently being presented to the user via the output unit 106.In the illustrated embodiment, the now-playing-indicator includes ahighlighted bar 710 surrounding a descriptor of a song title attribute706 and a graphical depiction of a speaker 712 emitting sound disposedwithin the highlighted bar 710.

Thus, FIG. 7 illustrates the result of a process wherein an interfacemodule 104 presenting the scaled image 602 (shown in FIG. 6) has beenengaged (e.g., touched) by a user at a location not corresponding to therevert-to-composite icon 604, the touch-sensitive display 204 of theengaged interface module 104 has generated an engagement signal, themodule controller component 312 of the engaged interface module 104 hasgenerated a selection signal containing module identifier informationand/or engagement-location information, the selection signal has beentransmitted to the main controller component 302 via the module and maincommunication components 316 and 310, respectively, and the maincontroller component 302 has generated image information at 412 basedupon the received selection signal. As described above, the drivercircuitry is therefore adapted to drive each interface module 104 withinthe array of interface modules to present a content-information image,associated with the scaled image, across the array of interface modulesbased upon an engagement signal generated by an engaged interface module104. That is, the driver circuitry is adapted to update the imagepresented across the array of interface modules based at least in partupon an engagement signal generated upon the user's engagement with aninterface module 104.

In one embodiment, a user may select a particular track to be presentedvia the output unit 106 by engaging (e.g., touching) an interface module104 within the array of interface modules at a location corresponding tothe descriptor of the song title attribute 706 associated with theparticular track (e.g., Hardgroove). Upon a user's engagement with thetouch-sensitive display 204, an engagement signal is generated andoutput to the module controller component 312 of the engaged interfacemodule 104. A selection signal containing module identifier informationand/or engagement-location information is then generated by the modulecontroller component 312 and transmitted to the main controllercomponent 302. The main controller component 302 generates imageinformation based upon the selection signal transmitted by the engagedinterface module 104 which, when converted into image data, is adaptedto drive one or more interface modules 104 within the array of interfacemodules to present the now-playing-indicator surrounding the descriptorof song title attribute 706 associated with the particular track.

In another embodiment, the image information generated at 412 furtherincludes icon-location information which, when converted into imagedata, is adapted to drive an interface module 104 (e.g., the top-rightinterface module 104 within the array of interface modules) to presentthe aforementioned revert-to-composite icon 604 in addition to arevert-to-scale icon 712 at predetermined locations on one or moreinterface modules 104 within the array of interface modules. While FIG.7 illustrates only one icon presented by only the top-right interfacemodule 104, it will be appreciated that one or more interface modules104 within the array of interface modules may be driven to present oneor more icons simultaneous with the presentation of thecontent-information image 702, as necessitated by the functionalityprovided by the interface apparatus. In one embodiment, therevert-to-scale icon 712 provides a visual indication of a locationwhere a user can engage an interface module 104 to cause the scaledimage 602, previously presented at 406, to be presented across the arrayof interface modules, instead of the content-information image 702.

Referring back to FIG. 4, at 414, an engagement signal is generated by atouch-sensitive display 204 of an interface module 104 driven to presentthe revert-to-composite icon 604 upon being engaged (e.g., touched) by auser at a location corresponding to where the revert-to-composite icon604 is presented. As similarly described above at 408, whenengagement-location information transmitted by the engaged interfacemodule 104 matches icon-location information generated at 412 thatcorresponds to the revert-to-composite icon 604, the main controllercomponent 302 generates image information as described above at 402which, when converted to image data, is adapted to drive each interfacemodule 104 within the array of interface modules to present a compositeimage across the array of interface modules. Accordingly, the drivercircuitry is adapted to update the image presented across the array ofinterface modules based at least in part upon an engagement signalgenerated upon the user's engagement with an interface module 104.

At 416, an engagement signal is generated by a touch-sensitive display204 of an interface module 104 driven to present the revert-to-scaleicon 712 upon being engaged (e.g., touched) by a user at a locationcorresponding to where the revert-to-scale icon 712 is presented. Whenengagement-location information transmitted by the engaged interfacemodule 104 matches icon-location information generated at 412 thatcorresponds to the revert-to-scale icon 712, the main controllercomponent 302 generates image information as described above at 406which, when converted to image data, is adapted to drive each interfacemodule 104 within the array of interface modules to present a scaledimage across the array of interface modules. Accordingly, the drivercircuitry is adapted to update the image presented across the array ofinterface modules based at least in part upon an engagement signalgenerated upon the user's engagement with an interface module 104.

As mentioned above, the main controller component 302 is adapted toaccess and output one or more media files to the output unit 106 basedupon information contained within selection signals transmitted byinterface modules 104 within the array of interface modules. In oneembodiment, the main controller component 302 may output a media file(or portion thereof) based upon information contained within a selectionsignal generated at 404 (i.e., after a user has engaged an interfacemodule 104 within the array of interface modules, driven to present acomposite image, thereby confirming the user's desire to output a mediafile visually identified by a constituent image presented by the engagedinterface module 104). In another embodiment, the main controllercomponent 302 may output a media file (or portion thereof) based uponinformation contained within a selection signal generated at 410 (i.e.,after a user has engaged an interface module 104 within the array ofinterface modules, driven to present a scaled image, thereby confirmingthe user's desire to output a media file visually identified by thescaled image presented across the array of interface modules 104). Inyet another embodiment, the main controller component 302 may output amedia file (or portion thereof) based upon information contained withina selection signal generated when the array of interface modules hasbeen driven to present a content-information image.

By driving the array of interface modules as described above in responseto a user's engagement with interface modules 104 within an array ofinterface modules, a user may easily select media files to be output tothe output unit 106. Moreover, by providing an array of interfacemodules, each with a touch-sensitive display 204, information associatedwith media files can be visually presented to the user in anaesthetically pleasing manner across a large image-presenting surface.Finally, because each touch-sensitive display 204 includes an e-inkdisplay, images presented to a user of the home AV system can have aunique, furniture-like quality.

As described above with respect to FIGS. 1-7 individual interfacemodules 104 within the array of interface modules can be engaged (e.g.,touched) by a user and aid the user in navigating through media filesvia the aforementioned composite, scaled, and content-informationimages. In one embodiment, however, an interface module 104 that isdetached from the main unit 102, but still communicatively coupled tothe main unit 102 (e.g., via the main and module communicationcomponents 310 and 316, respectively) can be engaged (e.g., touched) bythe user and driven to present the aforementioned composite, scaled, andcontent-information images on the touch-sensitive display 204 and/oracross the array of interface modules. Accordingly, a detached interfacemodule 104 may be used by a user as a “remote control” of the main unit102.

According to numerous embodiments disclosed herein, the interfaceapparatus described above with respect to FIGS. 1-3 also enables usersof the home AV system to control which output unit(s) media files are tobe output to in a simple, intuitive manner. FIG. 8 illustrates anembodiment of such an interface apparatus of the aforementionedexemplary home AV system 100.

As shown in FIG. 8, the interface apparatus exemplarily described abovewith respect to FIG. 1 further includes a remote unit 802 coupled to theoutput unit 106. Also shown in FIG. 8 are the main unit 102, theinterface modules 104, the output unit 106 containing the plurality ofspeakers 108, and the communication link 110. FIG. 8 also illustrateswherein one interface module 104 has been detached from the main unit102 and attached to the remote unit 802.

As illustrated in FIG. 8, the main unit 102 may be further adapted toassign one or more content-identifiers to one or more of theaforementioned interface modules 104 within the array of interfacemodules. Moreover, each interface module 104 may be further adapted tostore one or more content identifiers assigned by the main unit 102. Asmentioned above, each interface module 104 can be detachably coupled tothe main unit 102. Similarly, each interface module 104 can also bedetachably coupled to the remote unit 802 via any suitable means (e.g.,magnetically or mechanically via a tounge-in-groove arrangement betweencooperative surfaces of the main unit 102 and the interface modules 104,latch, clip, or the like, or combinations thereof).

FIG. 9 illustrates an exemplary functional block diagram of componentswithin the interface apparatus shown in FIG. 8. Generally, FIG. 9illustrates the remote unit 802 and an interface module 104. As shown,the remote unit 802 includes a remote controller component 902, a remoteoutput component 904, and a remote communication component 906. Asdescribed above with respect to FIG. 3, the interface module 104includes the module controller component 312, the optional module drivercomponent 314, the touch-sensitive display 204, and the modulecommunication component 316 in addition to a module memory 908.

As illustrated, the remote controller component 902 is connected to theremote output component 904 and the remote communication component 906while the module controller component 312 is connected to the modulecommunication component 316, the touch-sensitive display 204, and themodule memory 908.

The remote controller component 902 is adapted to access contentidentifiers stored within the module memory 908 and generate one or moremedia file request signals based on the content identifiers accessedfrom the module memory 908. In one embodiment, the media file requestsignal is adapted to cause the main unit 102 to output specific mediafiles (i.e., media files corresponding to the accessed contentidentifiers) to the output unit to which the associated remote unit 802is coupled. Accordingly, a media file request signal may, for example,include the aforementioned output unit address, identifying the outputunit 106 to which the associated remote unit 802 is coupled, and one ormore of the accessed content identifiers.

The remote output component 904 is adapted receive media file requestsignals generated by the remote controller component 902 and transmitthe generated media file request signals to the main unit 102. In oneembodiment, media file request signals may be transmitted to the mainunit 102 via the communication link 110.

The module and remote communication components 316 and 906,respectively, are adapted to communicate content identifier informationrepresenting assigned content identifiers from the interface module 104to the remote unit 802. Accordingly, the remote communication component906 is adapted to receive content identifier information transmitted bythe module communication component 316. In one embodiment, the moduleand remote communication components 316 and 906, respectively, areadapted to transmit/receive signals wirelessly between the remote unit802 and the interface module 104 and may, therefore, include anysuitable type of wireless receiver, transmitter, or transceiver. Forexample, the module and remote communication components 316 and 906,respectively, may each include an antenna coupled to a radio frequency(RF) receiver, transmitter, or transceiver. In one embodiment, themodule and remote communication components 316 and 906, respectively,may each be comprised within radio frequency identification (RFID)circuitry associated with the interface module 104 and remote unit 802,respectively, such that elements within the interface module 104 (e.g.,the module controller, driver, and communication components 312, 314,and 316, respectively, the touch-sensitive display 204, and the modulememory 908) receive sufficient electrical power to function as describedherein. Accordingly, and in one embodiment, the interface module 104 maynot include an internal power supply but, rather, operate based onelectricity generated by the interaction between the RFID circuitryassociated with the remote unit 802 and the interface module 104. Inanother embodiment, the module remote communication components 316 and906, respectively, may be adapted to communicate with each other via anon-RFID means such as Bluetooth, Wi-Fi, etc. When, for example, eitherBluetooth, Wi-Fi, or the like, are used, each interface module 104includes an internal battery which can be charged while the interfacemodule 104 is coupled to the main unit 102. When the internal battery ischarged, the electronics within the interface module 104 receivesufficient electrical power to function as described herein.

As mentioned above, the module memory 908 is adapted to store one ormore content identifiers assigned to the associated interface module 104by the main unit 102. In one embodiment, one or more content identifiersmay be assigned to interface modules 104 that are coupled to the mainunit 102. To assign a content identifier to an interface module 104, themain controller component 302 may, for example, output one or morecontent identifiers to the main communication component 310 and the maincommunication component 310 may then transmit the one or more contentidentifiers to the module communication component 316 of a particularinterface module 104. The received content identifier(s) are then outputto the module controller component 312 where they are subsequentlystored in the module memory 908.

In one embodiment, a content identifier assigned to a particularinterface module 104 within the array of interface modules correspondsto a content identifier identifying a media file visually identified bya constituent image 504, presented by the particular interface module104, and comprised within a composite image 502 presented across thearray of interface modules. In another embodiment, a content identifierassigned to any interface module 104 within the array of interfacemodules corresponds to a content identifier identifying a media filevisually identified by a scaled image 602 presented across the array ofinterface modules. Accordingly, when the main unit 102 assigns a contentidentifier to a particular interface module 104, the aforementioneddriver circuitry may drive the particular interface module 104 topresent an image corresponding to the scaled image 602 upon beingremoved from the array of interface modules. In a further embodiment, aninterface module 104 having an assigned content identifier storedtherein, presenting an image associated with the assigned contentidentifier, and detached from the main unit 102, may be used to controlthe outputting of a media file to the output unit 106. For example, uponcoupling the detached interface module 104 to the main unit, theassigned content identifier can be transmitted to the main controllercomponent 302 and the main controller component can cause a media fileassociated with the assigned content identifier to be subsequentlyoutput to the output unit 106. In another example, upon coupling thedetached interface module 104 to the main unit, the assigned contentidentifier can be transmitted to the main controller component 302 andthe driver circuitry can cause a scaled image to be presented across thearray of interface modules, wherein the scaled image corresponds to theimage presented by the previously-detached interface module 104.

In the embodiment illustrated in FIG. 9, the module controller component312 is further adapted to access content identifiers stored within themodule memory 908 and generate the aforementioned content identifierinformation based upon the accessed content identifiers.

FIG. 10 illustrates a flow chart describing one embodiment of a methodin which media files can be output to the output unit shown in FIG. 8.

At 1002, the remote unit 802 accesses a content identifier which hasbeen already been assigned to the interface module 104 according to, forexample, the process described above. In one embodiment, the assignedcontent identifier is accessed when the interface module 104 is attachedto (i.e., received by) the remote unit 802. Accordingly, the modulecontroller component 312 retrieves the assigned content identifierstored within the module memory 908, generates content identifierinformation representing the assigned content identifier and outputs thecontent identifier information to the module communication component316. The module communication component 316 then transmits the contentidentifier information to the remote unit 802 via the remotecommunication component 906 where it is subsequently output to theremote controller component 902.

At 1004, the remote controller component 902 generates a media filerequest signal based on the content identifier represented within thecontent identifier information output by the remote communicationcomponent 906. In one embodiment, the media file request signal isadapted to cause the main unit 102 to output the media file identifiedby the accessed content identifier to the output unit 106 that iscoupled to the remote unit 802. Accordingly, the media file requestsignal may, for example, contain the output unit address of the outputunit 106 that is coupled to the remote unit 802 and the accessed contentidentifier. The generated media file request signal is then output tothe remote output component 904 where it is subsequently transmitted tothe main unit 102 (e.g., via the communication link 110. At 1006, themain unit 102 responds to the media file request signal by outputtingthe media file identified by the accessed content identifier to theoutput unit 106 that is coupled to the remote unit 802 as describedabove.

By using the remote unit 802 and interface module 104 as described abovewith respect to FIGS. 8-10, a user is able to quickly and intuitivelycontrol to which output unit 106 (if more than one output unit exists)the main unit 102 should output a particular media file. Moreover,because the touch-sensitive display 204 can be provided as an e-inkdisplay, the interface module 104 can present an image indefinitelywithout requiring power and without having to be continuously driven bydriver circuitry. Accordingly, an interface module having a contentidentifier assigned thereto can be detached from both the main unit 102and the remote unit 802 and retain whatever image it was previouslydriven by the driver circuitry to present.

While the embodiments herein disclosed have been described by means ofspecific examples and applications thereof, numerous modifications andvariations could be made thereto by those skilled in the art withoutdeparting from the scope of the invention set forth in the claims.

1. An interface apparatus, comprising: a main unit adapted to causemedia files to be output to an output unit; an array of interfacemodules coupled to the main unit, the array of interface modules adaptedto present an image to a user, wherein each interface module in thearray of interface modules is adapted to be engaged by the user andgenerate a signal when engaged by the user; and driver circuitry adaptedto drive the array of interface modules to present an image to the userbased at least in part upon a signal generated by a user's engagementwith an interface module.
 2. The interface apparatus of claim 1, whereineach interface module in the array of interface modules comprises atouch-sensitive display adapted to generate the signal when engaged bythe user.
 3. The interface apparatus of claim 1, wherein each interfacemodule in the array of interface modules comprises an e-ink display. 4.The interface apparatus of claim 1, wherein the driver circuitry isadapted to drive each interface module based on output characteristicsof media files that the main unit can cause to be output at the outputunit to present a composite image across the array of interface modules,the composite image comprising a plurality of constituent images whereineach constituent image visually identifies a media file.
 5. Theinterface apparatus of claim 4, wherein the driver circuitry is adaptedto drive each interface module to present a constituent image.
 6. Theinterface apparatus of claim 5, wherein the driver circuitry is adaptedto drive each interface module to present a scaled image across thearray of interface modules based upon a signal generated by an interfacemodule driven to present the constituent image within the compositeimage.
 7. The interface apparatus of claim 6, wherein the drivercircuitry is adapted to drive each interface module to present acontent-information image across the array of interface modules, thecontent-information image corresponding to the scaled image presentedacross the array of interface modules.
 8. The interface apparatus ofclaim 1, further comprising a remote unit coupled to the output unit,wherein: the main unit is further adapted to assign a content identifierto an interface module of the array of interface modules, the contentidentifier identifying a media file; the interface modules are furtheradapted to be detachably coupled to the main unit and to the remoteunit; and the remote unit is adapted to: access the content identifierassigned to the interface module coupled thereto; and transmit a mediafile request signal to the main unit based on the content identifier,the media file request signal adapted to cause the main unit to output amedia file identified by the content identifier at the output unit. 9.The interface apparatus of claim 8, wherein the interface module isadapted to present an image after being detached from the main unit. 10.An interface apparatus, comprising: an interface module adapted to bedriven to present an image to a user; a main unit adapted to cause mediafiles to be output to an output unit, the main unit further adapted tobe detachably coupled to the interface module and, when coupled to theinterface module, to assign a content identifier to the interfacemodule, the content identifier identifying a media file; drivercircuitry adapted to drive the interface module to present an imagecorresponding to the assigned content identifier; and a remote unitcoupled to the output unit adapted to be detachably coupled to theinterface module, wherein when coupled to the interface module, theremote unit is adapted to: access the content identifier assigned to theinterface module coupled thereto; and transmit a media file requestsignal to the main unit based on the content identifier, the media filerequest signal adapted to cause the main unit to output a media fileidentified by the content identifier at the output unit.
 11. Theinterface apparatus of claim 10, wherein the interface module is adaptedto present an image after the main unit is detached from the interfacemodule.
 12. The interface apparatus of claim 11, wherein the interfacemodule comprises an e-ink display.
 13. An interface method, comprising:driving an array of interface modules coupled to a main unit to presentan image across the array of interface modules based upon outputcharacteristics of media files that the main unit can cause to be outputat an output unit; generating a signal upon a user's engagement with aninterface module; and updating the image presented across the array ofinterface modules based at least in part upon the signal generated uponthe user's engagement with the interface module.
 14. The interfacemethod of claim 13, further comprising generating the signal upon theuser's touching of a touch-sensitive display of an interface module. 15.The interface method of claim 13, further comprising driving eachinterface module based on output characteristics of media files that themain unit can cause to be output at the output unit to present acomposite image across the array of interface modules, the compositeimage comprising a plurality of constituent images wherein eachconstituent image visually identifies a media file.
 16. The interfacemethod of claim 15, further comprising driving each interface module topresent a constituent image.
 17. The interface method of claim 16,further comprising driving each interface module to present a scaledimage across the array of interface modules based upon a signalgenerated by an interface module driven to present the constituent imagewithin the composite image.
 18. The interface method of claim 17,further comprising driving each interface module to present acontent-information image across the array of interface modules, thecontent-information image corresponding to the scaled image presentedacross the array of interface modules.
 19. The interface method of claim13, further comprising assigning a content identifier to an interfacemodule of the array of interface modules, the content identifieridentifying a media file.
 20. The interface method of claim 19, furthercomprising receiving the interface module having the content identifierassigned thereto at a remote unit; accessing, at the remote unit, thecontent identifier assigned to the interface module; transmitting amedia file request signal from the remote unit to the main unit based onthe content identifier; and outputting a media file to the output unitfrom the main unit based upon the media file request signal, the outputmedia file being identified by at by the assigned content identifier.